Getting Started *************** Note: This documentation does not cover all concepts of MUI programming in detail. It's important that you also read the accompanying per class autodocs and have a look at the supplied demo programs! Object Oriented Programming =========================== The MUI system is based on BOOPSI, the Basic Object Oriented Programming System for Intuition. Understanding MUI and understanding this documentation requires at least a little knowledge about the concepts of object oriented programming, about classes, objects, methods and attributes. An absolutely sufficient introduction to these topics can be found in the "Libraries" part of the "ROM Kernel Reference Manuals" or in several Amiga mail articles. When talking about BOOPSI, most people automatically think of BOOPSI images and BOOPSI gadgets as part of the Amiga operating system. However, BOOPSI for itself is just a system for object oriented programming. One could e.g. have object oriented spread sheet software or object oriented file systems based on BOOPSI, intuition's builtin classes (gadgetclass, imageclass) are just two from thousands of possibilities. The MUI system also uses BOOPSI only as a base for object oriented programming. Thus, MUI classes are all subclasses of BOOPSI's rootclass and have nothing in common with the system supplied gadget or image classes. Unfortunately, Commodore missed some very important topics when designing these classes, disabling them for use in automatic layout systems such as MUI. Anyway, MUI features an interface to BOOPSI's gadgetclass and allows using already available gadgets (e.g. the Kick 3.x colorwheel) in MUI applications.


converted with guide2html by Kochtopf for the Meeting Pearls Vol.1